docs(factories): add quickstart - #517

HYC offered to be convinced on this one and deferred the call, so: keeping
it in Integrations rather than moving it to Factory configuration.

The page itself makes the argument. It opens with "Automation filters
decide which events from your connected tools start factory work", and its
core reference is a per-source table -- Slack, GitHub, GitLab, Linear --
whose rows link straight back to the integration pages listed directly
above it in the sidebar. It reads as the last step of wiring up a source:
you connect Slack, then you decide which Slack events should actually
start a run.

The argument for the other placement is that a filter is configuration,
which is true but does not separate it from anything. The integration
pages are configuration too. "Factory configuration" earns its name by
being scoped to the factory itself -- its agents, its definition files,
its infrastructure -- whereas a filter only means something once an
external tool is connected.

Easy to flip back if HYC disagrees: it is one line, and the reasoning is
in a comment next to it.

Also reconciled the branch with the base merge pushed onto it, which
brought in the quickstart rewrite and the new Troubleshooting page (#517).
Left Troubleshooting where HYC put it, inside the group this PR renamed to
Management & observability.

Co-Authored-By: Warp <agent@warp.dev>

…e rest of the docs (#556)

* docs(factories): make sidebar group and page names consistent

Per HYC: the Factories group names were the odd ones out, and the page
titles were inconsistent with each other.

Group labels. Every other tab names groups with noun phrases describing a
subject area -- "Agent configuration", "Triggers & integrations", "Plans
and billing", "Team management", "Security and compliance". Factories was
the only tab using bare imperatives, which is why "Configure / Connect /
Operate" read as belonging to a different product:

  Get started  -> Getting started
  Configure    -> Factory configuration
  Connect      -> Work intake
  Operate      -> Management & observability

"Getting started" matches the Terminal, Enterprise, and Guides tabs, which
all use the gerund. "Factory configuration" and "Management &
observability" are deliberate mirrors of the Automation Platform tab next
door, since the concepts are the same one level up: a control room is
where you watch a factory, and scorers are how you measure it.

"Work intake" needs more explanation. Those pages all answer the same
question -- how does work reach the factory -- across connections,
integrations, the filters deciding which events qualify, and the MCP that
hands work in. "Work item" and "intake" are the product's own vocabulary,
not docs coinage. "Integrations & intake" was the obvious alternative and
was rejected because it would nest an Integrations group inside a group
with Integrations in its name.

Page titles. The four integration pages used four different patterns:

  github   "GitHub integration"
  jira     "Connect Jira to your factory"
  linear   "Connect Linear to your factory"
  slack    "Connect a factory to Slack"

Standardized on "Connect {Service} to your factory", the pattern two of
them already used, rather than importing the Automation Platform tab's
"{Service} integration". That tab already has its own jira, linear,
github, and slack pages under that exact pattern, so reusing it would
create duplicate titles across the site -- something docs-seo-audit flags,
and which splits search intent between two pages that serve different
products. These pages are procedural anyway, so a task-oriented title fits.

Also:
- "The Factory control room" -> "Factory control room". No other page
  title in the tab opens with an article.
- The "How Warp Factories work" sidebar override was shadowing that page's
  own frontmatter label, "How Factories work". Aligned to the shorter one,
  since "Warp" is redundant inside the Factories tab and the sibling
  labels ("Factory agents", "Factory MCP") already drop it.

No slugs move, so no redirects are needed.

Left alone deliberately: HYC is adding a Troubleshooting section for
general Factory FAQs and doing a content cleanup pass once the outstanding
PRs land, so this change is naming only.

Not build-verified locally -- local builds have been unreliable in this
worktree. The sidebar edit is label strings plus comments, and the file
parses with balanced delimiters; CI covers the rest.

Co-Authored-By: Warp <agent@warp.dev>

* docs(factories): apply HYC feedback on the sidebar groups

Work intake -> Integrations, and Automation filters moves to Factory
configuration.

Renaming the group to "Integrations" meant the nested Integrations
subgroup had to go, or the sidebar would have read
Integrations > Integrations > Slack. Flattened it, so the four service
pages now sit directly in the group alongside "Connect your factory" as
its lead-in and Factory MCP at the end. That also drops the tab to two
levels throughout, matching every other group in it.

Automation filters is arguably intake rather than configuration, since
what it governs is inbound work. Going with HYC's placement: a filter is
something you define about your factory, next to its agents and its
definition files. Ordered so the group reads as who runs the work, how it
is defined, which work qualifies, and where it runs.

Resulting tab:

  Getting started            Overview / Quickstart / How Factories work
  Factory configuration      Factory agents / Definitions as code /
                             Automation filters / Infrastructure & security
  Integrations               Connect your factory / Slack / GitHub /
                             Linear / Jira / Factory MCP
  Management & observability Control room / Measure and improve

No slugs move, so no redirects are needed.

Co-Authored-By: Warp <agent@warp.dev>

* docs(factories): keep Automation filters with the integrations

HYC offered to be convinced on this one and deferred the call, so: keeping
it in Integrations rather than moving it to Factory configuration.

The page itself makes the argument. It opens with "Automation filters
decide which events from your connected tools start factory work", and its
core reference is a per-source table -- Slack, GitHub, GitLab, Linear --
whose rows link straight back to the integration pages listed directly
above it in the sidebar. It reads as the last step of wiring up a source:
you connect Slack, then you decide which Slack events should actually
start a run.

The argument for the other placement is that a filter is configuration,
which is true but does not separate it from anything. The integration
pages are configuration too. "Factory configuration" earns its name by
being scoped to the factory itself -- its agents, its definition files,
its infrastructure -- whereas a filter only means something once an
external tool is connected.

Easy to flip back if HYC disagrees: it is one line, and the reasoning is
in a comment next to it.

Also reconciled the branch with the base merge pushed onto it, which
brought in the quickstart rewrite and the new Troubleshooting page (#517).
Left Troubleshooting where HYC put it, inside the group this PR renamed to
Management & observability.

Co-Authored-By: Warp <agent@warp.dev>

---------

Co-authored-by: Warp <agent@warp.dev>
Co-authored-by: Hong Yi Chen <hongyi@warp.dev>